455594 - Datepicker doesn't respect locale.

Status: RESOLVED WORKSFORME

(MailNews Core :: XUL Replacements, defect)

Description

[Sebastian Winkler]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_5; en-us) AppleWebKit/528.4+ (KHTML, like Gecko) Version/3.1.2 Safari/525.20.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0

Datepicker uses a different date format from the one that nsIScriptableDateFormat determines.
It may be using the default formatting for the environment's language setting.
Anyway it can differ from the format that, for example, nc:parseType="Date" triggers in a tree.

Reproducible: Always

Comment 1

[Neil Deakin]

The datepicker uses the JavaScript date formatting api which uses the C strftime function. nsIScriptableDateFormat is used for formatting dates for display which the datepicker doesn't need to do.

Anyway, you haven't described what you think is wrong here, so closing as incomplete. If you think there is a bug here, reopen and describe what the actual bug is.

Comment 2

[Sebastian Winkler]

What I think is wrong is that the text representation of the date in a datepicker does not necessarily conform with the locale's format.
On my system, for example, the date September 22, 2008 is represented by the string "09/22/2008" in a datepicker, while a tree, if fed an rfc2822 date string marked as nc:parseType="Date", represents it as "22.09.2008". As does a textbox when set to a date value formatted with nsIScriptableDateFormat.

I will create attachments containing a testcase using nsIScriptableDateFormat and a screenshot of its appearance on my machine.

Comment 3

[Sebastian Winkler]

Attachment: testcase

This testcase is meant to compare the textual date formatting used be the datepicker widget to that obtained from nsIScriptableDateFormat.

Comment 4

[Sebastian Winkler]

Attachment: screenshot

This is how the testcase displays on my system.

Comment 5

[Andreas Wagner [:TheOne] [use NI]]

I can confirm this with Fx 3.5.1 on Mac OS X 10.5.7 (Intel) using german locale.

Comment 6

[Jonathan Kamens]

This bug is almost certainly completely obsolete at this point.